home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The CICA Windows Explosion!
/
The CICA Windows Explosion! - Disc 2.iso
/
pagemkr
/
pmtags.exe
/
PMTAGS.DOC
< prev
next >
Wrap
Text File
|
1993-10-20
|
8KB
|
188 lines
NAME:
PMTAGS - Check/fix style tags in PageMaker ASCII import files
SYNTAX:
pmtags [-f] [-h|?] [-sfile] [-v] [file...]
[file...] One or more ASCII text files prepared for importing
into PageMaker. Default extension is .TAG.
-f[output] Fix end-of-line's, paragraphs, style tags and other
formatting (where possible), writing output to
<input-file>.TXT.
-h, -? Display help information.
-sfile Specify an alternative file containing a list of valid style
names. If this option is not specified, the default name is
PMSTYLES.DAT. pmtags will search the current directory, the
directory where the pmtags executable (PMTAGS.EXE) resides,
and all directories on the path, for the file.
-v Verbose.
DESCRIPTION
PMTAGS reads an ASCII text file prepared for import into PageMaker, checking
for errors, and if the -f option is specified, creates a new file (with an
extension of .TAG) with extra CR and LF characters stripped out.
An ASCII file prepared for import into PageMaker contains style tags of the
form <stylename>, identifying the PageMaker style to be applied to the
paragraph.
PMTAGS reads information about the valid styles from PMSTYLES.DAT (or the
file specified with the -s option).
PMTAGS checks:
* that the style tag starts with "<" and ends with ">".
* that the style tag does not cross a line boundary.
* that the style tag starts in column 1.
* that the style tag is valid.
* that for specified styles, that style tag is followed by a certain
sequence of characters.
Each line in PMSTYLES.DAT contains the name of a style, optionally
followed by one of the following keywords:
LITERAL The text of this style is to be represented literally (e.g.
it might be used to represent computer input/output) and the
CR/LF characters are not removed from the end of each line.
CHECK=n The characters following the style tag are checked to make sure
that they are:
n=1 *\t[text]
n=2 \t[heading]\t
n=3 \t\t
n=4 [text]\t[text]
where \t is the TAB character, [text] is any printable
character(s) and [heading] is on of "Syntax", "Description",
"Examples", "Messages", "See Also" and "On-line Help".
COPYRIGHT
Copyright (c) 1992 Industrial Research Limited, Lower Hutt, New Zealand.
ERROR MESSAGES
Invalid command line argument - "x"
x is not a recognised command line argument. Type "pmtags -h" for
help.
Multiple file sets not supported - "&"
PMTAGS does not support the "&" multiple fileset separator (this is a
feature of the command line parser used). Re-issue the command without
the "&".
At least one file specification required
You must specify at least one file to process.
Will fix errors.
Informational message displayed when both the -f and -v command line
options are specified.
Can''t find style file <filename.ext>
PMTAGS could not locate the style file <filename.ext> in the
current directory, the directory where PMTAGS.EXE resides or a
directory specified in the PATH statement.
Can''t open style file <filename.ext>
PMTAGS was looking for the file <filename.ext> to load information about
valid styles, but could not find it. Check that the file exists in the
current directory, the directory where PMTAGS.EXE resides or a
directory specified in the PATH statement.
Loading style file <filename.ext>
Informational message produced (if the -v command line option was
specified) while PMTAGS is reading style information from the file
<filename.ext>.
Error reading style file <filename.ext>
PMTAGS couldn't read the style file <filename.ext>. Check the file is
not corrupt or the drive door open.
Too many styles - maximum allowed is 255
The style file contained definitions of more than 255 styles.
<text> is not a valid style attribute
The word <text> is not a valid style attribute. Currently, the only valid attributes
are LITERAL and CHECK=number.
<tag> is not a valid style tag
The word <tag> is not a correctly formed style tag - it must start with
a "<" and end with a ">".
Can''t open file <filename.ext>
PMTAGS could not open the input file <filename.ext>
Can''t create file <filename.ext>
PMTAGS could not create the output file <filename.ext>
Error closing file <filename.ext>
PMTAGS could not close the file <filename.ext>
Error writing to file <filename.ext>
There was an error writing to the output file <filename.ext>.
Check that the disk is not full, or the drive door open?
Error reading file <filename.ext>
at line <#>, column <#>
There was an error reading the input file <filename.ext> at the
position specified by the line and column values. Check that the file
is not corrupt and the drive door is closed.
filename.ext(line#): expecting "<characters>" after style tag "<tag>"
The characters following style tag <tag> did not match <characters>,
which may be one of "*\t[text]", "\t[heading]\t[text]", "\t\t[text]" or
"[text]\t[text]".
filename.ext(line#): "<heading>" not recognised heading for "<cmd-heading>"
Expecting one of "Syntax", "Description", "Examples", "Messages",
"See Also" or "On-line Help".
Check the spelling and case of <heading> carefully - it must match one
of the headings listed exactly.
filename.ext(line#): internal error in state machine; state=<#>, event=<#>
This indicates a major problem in the internal state machine of PMTAGS.
Contact the author.
filename.ext(line#): "<tag>" is a badly formed style tag
<tag> contains an embedded "<". Tags start with a "<", followed by
any characters other than "<>", and end with a ">".
filename.ext(line#): "<tag>" style tags may not cross line boundaries
The style tag <tag> is split across a line boundary; the most common
cause is the terminating ">" missing from the end of the style tag.
filename.ext(line#): <tag> style tag not at start of line
<tag> is a valid style tag but does not start in column 1.
filename.ext(line#): "<tag>" is not a valid style
<tag> starts in column 1 but is not a recognised style tag. If <tag>
is correct and not meant to be a style tag, move it away from column 1
to avoid confusing PageMaker.
filename.ext(line#): Is "<tag>" meant to be a style tag?
<tag> looks like a style tag (ie. starts with "<" and ends with ">")
but is not a recognised style tag and doesn't start in column 1. If
<tag> is correct, ignore the message.
filename.ext(line#): Pre-mature end of file
PMTAGS reached the end of the input file while still processing a style
tag (ie, the "<" had been seen, but not the terminating ">"), or still
checking characters following a style tag.
filename.ext(line#): <#> warnings, <#> errors
Informational message indicates the completion of processing of input
file <filename.ext>
filename.ext(line#): <#> warnings, <#> errors, created <filename.ext>
Informational message indicates the completion of processing of input
file <filename.ext>, and the creation of the outputfile <filename.ext>.PMTAGS v1.2 - Check/fix style tags in PageMaker ASCII import files